State change enabled by a hierarchical class of a radio access network device

ABSTRACT

Enabling a changing of a state of a device based on a hierarchical class of the device is disclosed. Non-macro radio access network (RAN) devices can be comprised in a network connected to a macro RAN device via a gateway RAN device. The gateway RAN device can be connected to a field RAN device via an intermediate RAN device. A state of a field RAN device can be altered based on a criterion. In an embodiment the criterion can be use of the hierarchical class of the RAN device, e.g., a field class RAN device, by an active or idle UE. In an embodiment the criterion can be use, by an active or idle UE, of another RAN device that is a logical neighbor to the field RAN device. Altering the state can result in a power savings or improved interference characteristics of the network.

RELATED APPLICATION

The subject application is a continuation of, and claims priority to,U.S. patent application Ser. No. 15/909,972, filed 1 Mar. 2018, andentitled “STATE CHANGE ENABLED BY A HIERARCHICAL CLASS OF A RADIO ACCESSNETWORK DEVICE,” which is a continuation of U.S. patent application Ser.No. 15/462,775, filed 17 Mar. 2017, and entitled “STATE CHANGE ENABLEDBY A HIERARCHICAL CLASS OF A RADIO ACCESS NETWORK DEVICE,” now issued asU.S. Pat. No. 9,930,617, the entireties of which application(s) arehereby incorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to enabling a changing of a stateof a device based on a hierarchical class of the device, e.g., enablingchanging to, or from, a lower power state for a radio access network(RAN) device based on a hierarchical class of the RAN device, forexample wherein the device is a femtocell, picocell, other small cell,access point (AP), etc.

BACKGROUND

A conventional heterogeneous radio access network (RAN) environment canencompasses conventional macro cells, small cells, e.g., femtocells,picocells, etc., and Wi-Fi access points. These conventionalheterogeneous RAN environments are becoming increasingly common toprovide mobile or wireless devices access to a network over a wirelesslink. Small cells can be a common part of 4G networks and can beexpected to similarly be common in the evolution of 5G networks. Someestimates propose that heterogeneous networks may be composed of 85%small cells and 15% macro cells by as early as 2020. Moreover, operationin the unlicensed spectral regions/bands is also becoming increasinglycommon in conventional heterogeneous networks. This can suggest that,increasingly, heterogeneous network architectures, possibly operating inthe unlicensed band, can place a high value on interference management.Similarly, energy conservation and management can become increasinglyimportant as more and more small devices are deployed in in theseheterogeneous networks. As such, businesses can be expected to strivefor efficient and be a responsible operation of network devices, e.g.,RAN devices, small cells, access points, etc.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example system that can enable changinga device state based on a hierarchical class of the device, inaccordance with aspects of the subject disclosure.

FIG. 2 is an illustration of an example system that can facilitatechanging a device state based on a hierarchical class of the deviceamong a plurality of devices comprising the device, in accordance withaspects of the subject disclosure.

FIG. 3 is an illustration of an example system that can facilitatechanging a device state based on a hierarchical class of the device anduse of another device in a network comprising the device and the otherdevice, in accordance with aspects of the subject disclosure.

FIG. 4 is an illustrates an example system that can facilitate changinga device state based on a hierarchical class of the device andneighboring device(s) state(s), in accordance with aspects of thesubject disclosure.

FIG. 5 is an illustration of an example system that can facilitatechanging a device state based on a hierarchical class of the device andreceived data, in accordance with aspects of the subject disclosure.

FIG. 6 illustrates a flowchart depicting adapting a state of a devicebased on a hierarchical class of the device, a state of a neighboringdevice, and a current state of the device, in accordance with aspects ofthe subject disclosure.

FIG. 7 illustrates an example method facilitating changing a devicestate based on a hierarchical class of the device, in accordance withaspects of the subject disclosure.

FIG. 8 illustrates an example method enabling time-delayed changing of adevice state based on a hierarchical class of the device, in accordancewith aspects of the subject disclosure.

FIG. 9 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 10 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

Modern radio access network (RANs) can comprise heterogeneous types ofRAN equipment in the RAN environment. These heterogeneous RAN devicescan encompasses conventional macro cells, small cells, e.g., femtocells,picocells, etc., Wi-Fi access points (Wi-Fi APs), millimeter-wavedevices, etc. Conventional heterogeneous RAN environments are becomingincreasingly common to provide mobile or wireless devices access to anetwork over a wireless link. Small cells can be a common part of 4Gnetworks and can be expected to similarly be common in the evolution of5G networks. Moreover, operation in the unlicensed spectralregions/bands is also becoming increasingly common in conventionalheterogeneous networks. It can therefore be expected that efficientpower and efficient spectral operation of network devices is desirable.Generally, in the context of this disclosure, the term ‘RAN device(s)’,or similar terms, can refer to non-macro cell devices, e.g., smallcells, Wi-Fi APs, other APs, etc., such as those associated withproviding enterprise level service(s), etc., and accordingly macro cellRAN devices will typically be referred to as ‘macro cell(s),’ ‘macro RANdevice(s)’, or similar terms to distinguish them from non-macro cell RANdevices.

Conventional RAN devices, e.g., deployed in enterprise environments,etc., can remain powered on and transmit wireless signals continuously,24 hours a day, even if there are no users in the building (e.g., afterhours, holidays and on weekends). This can needlessly waste resourcesand can generate spectrum interference, e.g., interfering with nearbyRAN devices and/or nearby macro RAN devices, because walls can fail toattenuate interfering radio frequency (RF) signals sufficiently. Assuch, there can be noteworthy leakage of RF signals from buildings thatcan interfere with other RAN and/or macro RAN devices. Devices thatgenerate interfering RF signals can be termed ‘interferes’. Moreover,these same interferers can also consume power even where they are notneeded to support current UE traffic.

A modern building can have multiple floors and each floor can havemultiple RAN devices to provide wireless coverage, e.g., wirelesscoverage to indoor spaces, nearby outdoor spaces affiliated with thebuilding, etc., hereinafter termed ‘indoor space(s)’ or similar terms,for clarity and brevity. Mobile device users enjoy seamless wirelessservice transitions between outdoor spaces and indoor spaces and toenable mobility from an outdoor space, associated with a macro RANdevice, to an indoor space, associated with a RAN device network,certain RAN devices in a building can be designated as “gateway” RANdevice(s). A gateway RAN device can be designated as a RAN devicelocated near an entrance point of a building. The gateway RAN device cantherefore be viewed as a RAN device that can have a neighbor relation toa macro RAN device to facilitate transitioning a mobile device from themacro service to the RAN service of the building. Moreover, other RANdevices of the building that are not designated as gateway RAN devicescan be termed field RAN devices. Field RAN devices generally will nothave a neighbor relation to a macro RAN device. Field RAN devices can,however, have a neighbor relationship with other RAN devices, e.g., agateway RAN device, another field RAN device, etc. These neighborrelationships between RAN devices can be created, maintained, destroyed,modified, etc., manually and/or autonomously, based on various methodsdevised to neighbor relationships, e.g., self-organizing behavior,self-optimizing behavior, etc.

In an aspect, determining a hierarchical class of a RAN device canenable adaptation of a state of the device. In an embodiment, RANdevices can be classed as gateway RAN devices, field RAN devices, andintermediate RAN devices. A gateway RAN device can be affiliated with anentry point to a network, e.g., an entry to a building, an entry to apark, an entry to a mine, etc. A gateway RAN device can typically have aneighbor relation to a macro RAN device to enable transition of a userequipment from a macro network to a network attached to the macronetwork via the gateway RAN device. An intermediate RAN device can havea neighbor relationship with a gateway RAN device and a field RANdevice. A field RAN device can have neighbor relations with other fieldRAN device(s) or an intermediate RAN device, but will not have aneighbor relation with a gateway RAN device or a macro RAN device, e.g.,a field device that has a neighbor relation with a gateway RAN device istypically an intermediate RAN device, a field device that has a neighborrelation to a macro RAN device is typically a gateway RAN device. Itwill be noted that a gateway RAN device, an intermediate RAN device,and/or a field RAN device can be identical devices that have differentneighbor relations, can be different devices, e.g., different types ofdevice, differently configured same devices, etc., that have differentneighbor relations. In an aspect, a gateway RAN device can be a firsthierarchical class, an intermediate RAN device can be a secondhierarchical class, and a field RAN device can be a third hierarchicalclass, wherein the classes differ based on neighbor relationships andcorresponding differences in functionality, rather than explicitly bythe type or configuration of a device. As an example, a first RAN devicecan be a field RAN device that can be moved to a building entry pointand can be designated as a gateway RAN device allowing the first deviceto have a neighbor relationship with a macro RAN device. As a secondexample, a gateway RAN device can be re-designated as a field RAN deviceallowing only neighbor relationships with other field RAN devices andintermediate RAN devices.

The use of hierarchical RAN device classes can enable state transitionsof RAN devices. These state transitions can in some embodiments reducethe likelihood that a RAN device is an interferer, e.g., the RAN devicecan be an interferer less often, etc. These state transitions can insome embodiments reduce the power consumed by RAN devices. As anexample, a state transition can be from a full power state, e.g.,receive/transmit at full strength, etc., to a sleep state, e.g., reducedtransmission of RF signals, etc., to an off state, e.g., the RAN devicepowers off and draws no power. In this example, power consumption isreduced and the RAN device can be less of an interferer.

In an aspect, state transitions can be controlled by the RAN deviceitself, can be controlled by a local controller communicatively coupledto the RAN device, can be centrally controlled by a remotely locatedcontroller via a macro communication network, etc. As an example, eachsmall cell or AP can report its traffic load to a smart controller. Theexample smart controller can be a logical entity and could be alocalized in building, could be centralized in a network operator'slocation, virtualized in a cloud-based environment, etc. In someembodiments, control can be integrated as one of the functions in anexisting system, e.g., a self-organizing network (SON) controller,within a RAN device itself, etc. A controller, based on a parameter,such as the hierarchical class of the RAN device, use of a RAN deviceand/or a coupled RAN device, supplementary data, e.g., date (weekday,weekend, national or company holiday), time (regular working hours,after hours), historical use data, etc., rules, received indicia, etc.,can determine if a state transition is allowed, can determine toinitiate a state transition, can adapt a RAN device state, etc. As anexample, a virtualized controller can activate a ‘power saving’ mode ona RAN device, via a signal sent to the RAN device over a communicationframework, based on the RAN device being a field RAN device and allneighboring RAN devices indicating that they are without a camped or inuse UE. In some embodiments, a controller can ‘learn’ or form inferencesbased on historical usage, e.g., usage patterns of a RAN device at aparticular location, etc., and can use learned behavior(s),inference(s), etc., as an input to a decision making process regardingthe state transition. As an example, a field RAN device can learn thatit is typically used between 6 am and 6 pm, Monday to Friday, and canaccordingly not check for possibilities of a state transition duringthose hours. In an aspect, over a period of time, more especially in alarge location with potentially tens to thousands of RAN devices, thedisclosed subject matter can result in notable energy savings and, insome embodiments, can concurrently provide a less cluttered spectrum.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages, and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which can facilitate changinga device state based on a hierarchical class of the device, inaccordance with aspects of the subject disclosure. System 100 cancomprise macro RAN device 102. Macro RAN device 102 can be an accesspoint to a macro network, e.g., a macro cellular device, a NodeB, aneNodeB, a wide area network (WAN) AP, etc. In some embodiments, macroRAN device 102 can be connected to a communications network associatedwith a wireless network provider identity. Typically, a user equipment(UE) can communicate via a wireless interface to macro RAN device 102.The UE can be transferred from macro RAN device 102 to another macro RANdevice as the UE moves between a location served by macro RAN device 102and a location served by the other macro RAN device, e.g., a cellularhandover, etc. In an aspect, macro RAN device 102 can be a neighbor of agateway RAN device, e.g., RAN device 110.

System 100 can comprise RAN device 110. Ran device 110 can be a gatewayRAN device. A gateway RAN device, e.g., RAN device 110, can have aneighbor relationship with macro RAN device 102. Accordingly, a UE cantransition, e.g., be handed over, between RAN device 110 and macro RANdevice 102. As an example, where a UE is transported into an officebuilding, over the air communication to macro RAN device 102 can degradedue to RF attenuation associated with the building, etc. The example UEcan seek to transition to another RAN access device to maintain UEservices. Accordingly, where the example building comprises RAN device110, the UE can be handed from macro RAN device 102 to RAN device 110based on the neighbor relationship between macro RAN device 102 and RANdevice 110. In contrast, for example where a neighbor relationship doesnot exist between macro RAN device 102 and RAN device 110, the UE can bedropped from macro RAN device 102 before acquiring service via RANdevice 110, which can result in an interruption of UE services. WhereRAN device 110 is a gateway RAN device, in some embodiments, RAN device110 can be have a neighbor relationship with RAN device 120.

RAN device 120, of system 100, can be an intermediate RAN device. In anaspect, an intermediate RAN device can have a neighbor relation with afield RAN device, another intermediate RAN device, and/or a gateway RANdevice. In an aspect, an intermediate RAN device, e.g., RAN device 120,can be interposed between a field RAN device and a gateway RAN device,wherein the gateway RAN device can be interposed between macro RANdevice 102 and the intermediate RAN device. In some embodiments,intermediate RAN device, e.g., RAN device 102, etc., can be a firstlayer of RAN devices that can support a transition to/from a gateway RANdevice.

System 100 can further comprise RAN device 130 that can have a neighborrelationship with RAN device 120. RAN device 130 can be a field RANdevice. In an aspect, a field RAN device, e.g., RAN device 120, etc.,can have a neighbor relationship with other field RAN devices and/or anintermediate RAN device, e.g., RAN device 120. As such, in someembodiments, a field RAN device, e.g., RAN device 120, etc., can be atleast one hierarchical layer away from a gateway RAN device, e.g., RANdevice 110, etc.

In an aspect, a RAN device can be enabled to undergo a state transitionbased on satisfying a hierarchical class rule. The hierarchical classrule can, for example, reserve state transitions for field RAN device(s)only, e.g., an intermediate RAN device and/or a gateway RAN device canbe deemed ineligible to undergo a state transition. Moreover,eligibility to undergo a state transition can be distinct fromdetermining if a state transition is to be initiated or performed. As anexample, a field RAN device, e.g., RAN device 130, etc., can bedetermined to be eligible for a state transition but may, or may not,undergo a state transition based on a further criterion, e.g., the fieldRAN device is not in use by a UE, etc.

In an embodiment, where RAN device 130 is eligible to undergo a statetransition, a state transition of RAN device 130 can be initiated inresponse to determining that a self-use rule related to use of RAN 130has been satisfied and that a neighbor-use rule related to use of RAN120 has been satisfied. In an aspect, the neighbor use rule is relatedto use of a neighbor RAN device to RAN device 130 rather than to use ofan intermediate RAN device, e.g., RAN device, etc., specifically. As anexample, where RAN device 130 has a neighbor relationship to anotherfield RAN device, rather than to an intermediate RAN device like 120,and the other field RAN device is in use by a UE, then a statetransition may not be initiated based on a possibility of the UEtransitioning from the neighboring field RAN device to RAN device 130.Use of a RAN device can include active and idle use, e.g., active usecan be based on a radio access bearer resource being established for theUE via the RAN device while idle use can lack the radio access bearerresource but still have the UE logically camped on the RAN device.

FIG. 2 is an illustration of a system 200, which can facilitate changinga device state based on a hierarchical class of the device among aplurality of devices comprising the device, in accordance with aspectsof the subject disclosure. System 200 can comprise macro RAN device 202.Macro RAN device 202 can be an access point to a macro network. In someembodiments, macro RAN device 202 can be connected to a communicationsnetwork associated with a wireless network provider identity. Typically,a UE can communicate via a wireless interface to macro RAN device 202.The UE can be transferred from macro RAN device 202 to another macro RANdevice as the UE moves between a location served by macro RAN device 202and a location served by the other macro RAN device.

System 200 can comprise RAN device 210. Ran device 210 can be a gatewayRAN device. A gateway RAN device, e.g., RAN device 210, can have aneighbor relationship with macro RAN device 202. Accordingly, a UE cantransition between RAN device 210 and macro RAN device 202. In someembodiments, RAN device 210 can further have a neighbor relationshipwith RAN device(s) 221-223, etc.

RAN device(s) 221-223, of system 200, can be intermediate RAN device(s).In an aspect, an intermediate RAN device can have a neighbor relationwith a field RAN device, another intermediate RAN device, and/or agateway RAN device, as illustrated. As an example, RAN device 221 canhave a neighbor relationship with gateway RAN device 210 and field RANdevice 231. As another example, RAN device 222 can have a neighborrelationship with gateway RAN device 210 and field RAN devices 232 and233, as well as to another intermediate RAN device, e.g., RAN device223. As a further example, RAN device 223 can have a neighborrelationship with gateway RAN device 210 and intermediate RAN device222. Of note, intermediate RAN device(s) 221-223 do not have a neighborrelationship with macro RAN device 202, e.g., in some embodiments, onlya gateway RAN device, e.g., 210, can have a neighbor relationship with amacro RAN device, e.g., 202. In an aspect, an intermediate RAN device,221-223, can be interposed between a field RAN device, e.g., 231-237,and a gateway RAN device, e.g., 210. Moreover, a gateway RAN device,e.g., 210, can be interposed between macro RAN device 202 andintermediate RAN device(s), e.g., 221-223. In some embodiments,intermediate RAN devices can be a first layer of RAN devices that cansupport a transition between a gateway RAN device and a field RANdevice.

System 200 can further comprise field RAN device(s) 231-237 that canhave a neighbor relationship with intermediate RAN device(s) 221-223, asillustrated. A field RAN device, 231-237, can have a neighborrelationship with other field RAN devices 231-237, and/or intermediateRAN device(s), 221-223. As an example, field RAN device 231 can have aneighbor relationship with intermediate RAN device 221 and field RANdevice 232. As another example, field RAN device 234 can have a neighborrelationship with field RAN device 233, field RAN device 236, field RANdevice 237, field RAN device 235, and field RAN device 233, but not haveone with an intermediate RAN device, 221-223, nor with a gateway RANdevice 210, nor macro RAN device 202. As such, in some embodiments, afield RAN device, 231-237, can be at least one hierarchical layer awayfrom a gateway RAN device, 210, e.g., separated by at least intermediateRAN device 221-223.

In an aspect, a RAN device can be enabled to undergo a state transitionbased on satisfying a hierarchical class rule. The hierarchical classrule can, for example, reserve state transitions for field RAN device(s)231-237 only, e.g., an intermediate RAN device 221-223, and/or a gatewayRAN device 210 can be deemed ineligible to undergo a state transition.Moreover, eligibility to undergo a state transition can be distinct fromdetermining if a state transition is to be initiated or performed. In anembodiment, where a field RAN device, 231-237, is eligible to undergo astate transition, the state transition of the field RAN device, 231-237,can be initiated in response to determining that a self-use rule relatedto UE use of field RAN device, 231-237, has been satisfied and that aneighbor-use rule related to UE use of a neighboring RAN device, e.g.,field RAN device, 231-237, and/or intermediate RAN device 221-223, hasbeen satisfied. In an aspect, the neighbor use rule is related to use ofa neighbor RAN device to RAN device 230 rather than to use of anintermediate RAN device, e.g., RAN device, etc., specifically. As afirst example, where RAN device 231 has a neighbor relationship to fieldRAN device 232 and to intermediate RAN device 221, then UE use of fieldRAN device 231 or 232, or UE use of field RAN device 221, can restrictimplementation of a state transition for filed RAN device 231 even wherefield RAN device 231 is eligible for a state transition. As a secondexample, where RAN device 235 has a neighbor relationship to field RANdevices 233, 234, and 237, then UE use of field RAN device 233, 234,235, or 237, can restrict implementation of a state transition for fieldRAN device 235 even where field RAN device 235 is eligible to otherwiseundergo a state transition.

FIG. 3 is an illustration of a system 300, which can facilitate changinga device state based on a hierarchical class of the device and use ofanother device in a network comprising the device and the other device,in accordance with aspects of the subject disclosure. System 300 cancomprise macro RAN device 302. Macro RAN device 302 can be an accesspoint to a macro network. In some embodiments, macro RAN device 302 canbe connected to a communications network associated with a wirelessnetwork provider identity. Typically, a UE can communicate via awireless interface to macro RAN device 302. The UE can be transferredfrom macro RAN device 302 to another macro RAN device as the UE movesbetween a location served by macro RAN device 302 and a location servedby the other macro RAN device.

System 300 can comprise gateway RAN device 310. Gateway RAN device canhave a neighbor relationship with macro RAN device 302. Accordingly, aUE can transition between gateway RAN device 310 and macro RAN device302. In some embodiments, gateway RAN device 310 can further have aneighbor relationship with intermediate RAN device 320.

Intermediate RAN device 320, of system 300, can have a neighbor relationwith a field RAN device, e.g., 332-338, another intermediate RAN device,not illustrated, and/or a gateway RAN device, e.g., 310, as illustrated.As an example, intermediate RAN device 320 can have a neighborrelationship with gateway RAN device 310 and field RAN device 332. Ofnote, intermediate RAN device 320 does not have a neighbor relationshipwith macro RAN device 302, e.g., in some embodiments, only gateway RANdevice 310 can have a neighbor relationship with macro RAN device 302.In an aspect, an intermediate RAN device 320 can be interposed between afield RAN device, e.g., 332-338, and gateway RAN device 310. Moreover,gateway RAN device 310 can be interposed between macro RAN device 302and intermediate RAN device 320. In some embodiments, intermediate RANdevices can be a first layer of RAN devices that can support a UEtransition between a gateway RAN device and a field RAN device via theintermediate RAN device.

System 300 can further comprise field RAN device(s) 332-338 that canhave a neighbor relationship with intermediate RAN device 320, or withother field RAN devices 332-338, as illustrated. As an example, fieldRAN device 332 can have a neighbor relationship with intermediate RANdevice 320 and field RAN device 334. As another example, field RANdevice 334 can have a neighbor relationship with field RAN device 332,field RAN device 336, but not have a neighbor relationship with anintermediate RAN device, 320, with a gateway RAN device, 310, nor with amacro RAN device, 302. As such, in some embodiments, a field RAN device,332-338, can be at least one hierarchical layer away from gateway RANdevice 310, e.g., separated by at least intermediate RAN device 320.

In an aspect, a RAN device can be enabled to undergo a state transitionbased on satisfying a hierarchical class rule. The hierarchical classrule can, for example, reserve state transitions for field RAN device(s)332-338 only, e.g., intermediate RAN device 320, and/or a gateway RANdevice 310 can be deemed ineligible to undergo a state transition.Moreover, eligibility to undergo a state transition can be distinct fromdetermining if a state transition is to be initiated or performed. In anembodiment, where field RAN device, 332-338, are eligible to undergo astate transition, the state transition of the field RAN device, 332-338,can be initiated in response to determining that a self-use rule relatedto UE use of field RAN device, 332-338, has been satisfied and that aneighbor-use rule related to UE use of a neighboring RAN device, e.g.,field RAN device, 332-338, and/or intermediate RAN device 320, has beensatisfied. As a first example, RAN device 332 can have a neighborrelationship to field RAN device 334 and to intermediate RAN device 320,such that UE use of field RAN device 332, 334, or UE use of field RANdevice 320, can cause either the self-use or neighbor-use rule to not besatisfied, thwarting implementation of a state transition for field RANdevice 331. System 300 illustrates this by showing UE 304 using fieldRAN device 332, which can cause the self-use rule to be unsatisfied andcan result in no state transition being initiated. As a second example,where RAN device 336 has a neighbor relationship to field RAN devices334 and 338, and UE 304 uses field RAN device 332 rather than 334 or338, then both the self-use and neighbor-use rule can be satisfied. Itwill be noted that in some embodiments, the neighbor-use rule can beadapted to reflect more than a first layer of neighbor RAN device. Inthese embodiments, UE 304 use of 332 can affect satisfaction of theneighbor-use rule, for example for field RAN device 336, 338, etc. Insome embodiments, the neighbor-use rule can be based on the density ofRAN devices, e.g., where the devices are dense, it can be more likelythat a transition between a used and unused RAN device can occur rapidlyenough in time that it can be desirable to avoid state transitions for aplurality of layers between an in use RAN device and an eligible RANdevice.

FIG. 4 is an illustration of a system 400, which can facilitate changinga device state based on a hierarchical class of the device andneighboring device(s) state(s), in accordance with aspects of thesubject disclosure. System 400 can comprise macro RAN device 402. MacroRAN device 402 can be an access point to a macro network. In someembodiments, macro RAN device 402 can be connected to a communicationsnetwork associated with a wireless network provider identity. Typically,a UE can communicate via a wireless interface to macro RAN device 402.The UE can be transferred from macro RAN device 402 to another macro RANdevice as the UE moves between a location served by macro RAN device 402and a location served by the other macro RAN device.

System 400 can comprise gateway RAN device 410. Gateway RAN device canhave a neighbor relationship with macro RAN device 402. Accordingly, aUE can transition between gateway RAN device 410 and macro RAN device402. In some embodiments, gateway RAN device 410 can further have aneighbor relationship with intermediate RAN device 420. Intermediate RANdevice 420, of system 400, can have a neighbor relation with a field RANdevice(s), e.g., 430, 432, 434, etc. another intermediate RAN device,not illustrated, and/or a gateway RAN device, e.g., 410, as illustrated.

System 400 can further comprise field RAN device(s) 430, 432, 434, etc.,that can have a neighbor relationship with other field RAN devices 430,432, 434, etc., as illustrated. In an embodiment, field RAN device 434can have neighbor relations with a first layer of other field RANdevices as indicated by the medium grey band of field RAN devices 432,surrounding field RAN device 434. Field RAN device 434 can have extendedneighbor relations with a second layer of other field RAN devices, e.g.,the neighbors of the first layer can be extended neighbors of 434, asindicated by the light grey band of field RAN devices 430, surroundingthe first layer of field RAN 432. As such, in some embodiments, fieldRAN device 434 can be at least one hierarchical layer away from gatewayRAN device 410, e.g., separated by at least intermediate RAN device 420,and generally one or more layers of filed RAN devices, e.g., 430, 432,434, etc.

In an aspect, a RAN device can be enabled to undergo a state transitionbased on satisfying a hierarchical class rule. The hierarchical classrule can, for example, reserve state transitions for field RAN device(s)430-434 only, e.g., intermediate RAN device 420, and/or a gateway RANdevice 410 can be deemed ineligible to undergo a state transition.Moreover, eligibility to undergo a state transition can be distinct fromdetermining if a state transition is to be initiated or performed. In anembodiment, where field RAN device 434 is eligible to undergo a statetransition, the state transition of the field RAN device 434 can beinitiated in response to determining that a self-use rule related to UEuse of field RAN device 434 has been satisfied and that a neighbor-userule related to UE use of a neighboring RAN device, e.g., field RANdevice, 432 has been satisfied. As such, UE use of any of the field RANdevices 432 can prevent initiation of a state transition for the fieldRAN device 434, for example, because there is a possibility of a UEtransitioning from a neighboring field RAN device 432 to field RANdevice 434. This can be understood more clearly where the statetransition is putting field RAN device 434 into a low-power state, inthat if a UE attached to field RAN device 432 attempts to transition tofield RAN device 434, the time it takes to bring field RAN device 434out of a low-power state can cause transition problems and, as such, adirect neighbor that has a UE attached can be used to prevent aneligible RAN device from undergoing a state transition. In someembodiments, the neighbor-user rule can extend beyond the first layer ofneighbor RAN device, e.g., field RAN devices 432 are the first layer tofield RAN device 434. In these embodiments, use of a second, third,etc., layer RAN device can affect the implementation of a statetransition for an eligible RAN device. As an example, the UE use of thesecond layer field RAN devices 430 to field RAN device 434 can prevent astate transition for field RAN device 434.

FIG. 5 is an illustration of a system 500, which can facilitate changinga device state, based on a hierarchical class of the device and receiveddata, in accordance with aspects of the subject disclosure. System 500can comprise small cell/AP/RAN device 540, hereinafter RAN device 540.RAN device 540 can be the same as or similar to RAN device(s) 110, 120,130, 210, 221-223, 231-237, 310, 320, 332-338, 410, 420, 430, 432, 434,etc. RAN device 540 can comprise hierarchy analysis component (HAC) 542.HAC 542 can determine a hierarchical class of a RAN device, e.g., 540,etc. In an embodiment, the hierarchical class can be a gateway RANdevice, an intermediate RAN device, a field RAN device, etc., asdisclosed herein. In an aspect, additional hierarchical classes can beemployed, e.g., a first layer of neighbor RAN device, a second layer ofRAN devices, etc. In an aspect, HAC 542 can determine a hierarchicallevel of RAN 540, of other RAN devices, e.g., first layer neighbors,second layer neighbors, etc. In an embodiment, HAC 542 can determine ahieratical map of RAN devices in a device network, a portion of a devicenetwork, etc. The device map and/or hierarchical class informationdetermined by HAC 542 can be employed in determining eligibility for astate transition of a RAN device. Moreover, the device map and/orhierarchical class information determined by HAC 542 can be employed inself-use and neighbor-use rule analysis.

RAN device 540 can further comprise state determination component (SDC)544. SDC 544 can determine the current or historical state of RAN 540,via self-state component 550, or of another RAN device, vianeighbor-state component 552. A state diagram or model thereof can thenbe used to determine possible state transitions from the current statedetermined by SDC 544. In an aspect, a current state can compriseinformation indicative of UE use of a RAN device. As an example, SDC 544can determine, via self-state component 550, if RAN device 540 is in useby a UE, e.g., a UE is camped on RAN device 540, is actively using RANdevice 540, etc. As another example, SDC 544 can determine, vianeighbor-state component 552, if another RAN device, e.g., a neighbor toRAN Device 540, etc., is in use by a UE.

In an embodiment, HAC 542 and SDC 544 can be coupled to rule component546. Rule component 546 can receive hierarchical data from HAC 542 andcan receive state data from SDC 544. Rule component 546 can furtherreceive input and/or supplemental data 570 from another device. In anembodiment, data 570 can comprise data that allows implementation of newrules, deletion of existing rules, modification of existing rules, etc.,comprised in rule component 546. In some embodiments, data 570 cancomprise information relation to historical RAN device use, events data,time, date, location, etc. In an embodiment, rule component 546 canenable determining state transition eligibility of RAN device 540, or ofanother RAN device. Moreover, rule component 546 can determine if astate transition in to be performed, initiated, etc., based on the RANdevice being deemed eligible and satisfaction of rules related to use,time/date/place, historical data, etc. As an example, historical dataindicating regular use of a RAN device during working hours can preventa RAN device from going into a sleep mode during business hours eventhough it is otherwise eligible and unused. As a further example,historical data indicating irregular use of a RAN device during workinghours can limit the RAN device to a ‘snoozing’ mode rather than a ‘deepsleep’ mode during business hours where it is eligible and unused, e.g.,the RAN can stay active but broadcast an SSID less frequently that whenat full power, which can save power and reduce interference but allowthe RAN device to rapidly support an incoming UE.

RAN device 540 can comprise state adjustment component (SAC) 548. SAC548 can initiate, implement, or perform a state transition based oninformation from rule component 546. In an aspect, rule component 546can indicate which rules are satisfied and SAC 546 can, accordingly,determine what state transition(s) to implement. In an embodiment, SAC548 can comprise snooze component 560, sleep component 562, offcomponent 546, etc. Snooze component 560 can enable putting a RANdevice, e.g., 540, etc., into a snooze mode that can be more power andinterference friendly than a full power mode but less so than a sleepmode. Sleep component 562 can enable putting a RAN device, e.g., 540,etc., into a sleep mode that can be more power and interference friendlythan either a full power mode or a snooze mode, but less so than an offmode. Off component 564 can enable putting a RAN device, e.g., 540,etc., into an off state that can be consume little to no power and causelittle to no interference but can be much slower to transition out of incomparison to a sleep or snooze state. It will be appreciated that otherstates can be represent by components of SAC 548 and that all such otherstates are within the scope of the instant disclosure despite not beingexplicitly recited for the sake of clarity and brevity.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 is an illustration of a flowchart 600, which can facilitateadapting a state of a device based on a hierarchical class of thedevice, a state of a neighboring device, and a current state of thedevice, in accordance with aspects of the subject disclosure. Flowchart600 can comprise a controller determining if a RAN device is a gatewaydevice at decision 610. A gateway RAN device can be designated as a RANdevice that has a neighbor relation to a macro RAN device. Where the RANdevice is determined to be a gateway device the RAN device can be set totype ‘A’ at 605. Where the RAN device is determined to not be a gatewaydevice, e.g., the RAN device does not have a neighbor relation with amacro RAN device, then the device type can be set to type ‘B’ at 615.

At 620, flowchart 600 can comprise the controller determining if the RANdevice is coupled to a gateway RAN device. Devices coupled to a gatewayRAN device can be type ‘B’ devices or other RAN devices. Where the RANdevice is determined to be coupled to a gateway RAN device the flow canreturn to decision block 610. Where the RAN device is determined by thecontroller to not be coupled to a gateway RAN device, the type can beset to type ‘C’ at 625. In an aspect, type A can be a gateway RANdevice, type B can be an intermediate RAN device, and type C can be afield RAN device, as disclosed hereinabove.

At 630, it can be determined by the controller if another RAN deviceneighboring the RAN device is supporting a UE. In an aspect, supportinga UE can comprise a UE being camped on the neighboring RAN device. Inanother aspect, supporting a UE can comprise the UE having an activesession with the neighboring RAN device, e.g., having a radio accessbearer established via the neighboring RAN device. Where the neighboringRAN device is supporting a UE, the controller can return to 610. Wherethe neighboring RAN device is not supporting a UE, an indication that astate change is available can be made by the controller at 635.

At 640, it can be determined by the controller if the RAN device itselfis supporting a UE. If the RAN device is itself supporting a UE, thecontroller can return to 630. This can allow the controller to continueto monitor for UE use of the RAN device itself or of a neighboring RANdevice before determining to initiate a state transition. Where the RANdevice itself is not supporting a UE, it can be determined by thecontroller, at 650, if a current use rule is satisfied. Satisfaction ofthe current use rule can be based on historical use data, supplementarydata, e.g., time/date/location, an event occurrence, etc. Again, if thecurrent use rule is not satisfied, the controller can return to 630 toallow the controller to continue to monitor relevant conditions of theRAN device prior to determining to initiate a state transition. If thecurrent use rule is satisfied at 650, the state of the RAN device can beadapted by the controller via a state transition at 655.

At 660, the controller can monitor for a recovery indicator related tothe RAN device. Where a recovery indicator has been received, e.g., anindicator indicating that the RAN device should return to a full powerstate, that the RAN device should transition to another state, etc.,then the controller can adapt the state of the device via a statetransition at 665, then the controller can return to 610. Where arecovery indicator has not been received at the controller, then thecontroller can return to 660 to continue to monitor of a recoveryindicator.

FIG. 7 illustrates example method 700 that facilitates changing a devicestate based on a hierarchical class of the device, in accordance withaspects of the subject disclosure. Method 700, at 710, can comprise, inresponse to determining that a device state change is supported,determining that a rule related to a present use of the device has beensatisfied. The device state change can be determined to be supportedbased on the hierarchical class of the device. The hierarchical classcan be related to a logical functionality of a device or to a type of adevice. In an aspect, logical function of a device can be determined toact as a gateway device, an intermediate device, or a field device, evenwhere the devices are otherwise the same or similar. In another aspect,different types of devices can be used for the different hierarchicalclasses, e.g., a first type of device can be used as a gateway device, asecond type of device can be used for an intermediate device, and athird type of device can be used for a field device, wherein the first,second and third types of device can be different types.

In response to determining that the hierarchical class of device enablesthe device to undergo a state change, rules relating to a current use ofthe device can be employed to determine that the state change of thedevice should be initiated. In an aspect, the current use can relate tothe device supporting a UE, e.g., an idle UE camped on the device, anactive UE having a radio access bearer resource allocated via thedevice, etc. In some embodiments, current use can be based on UE use ofneighboring devices, e.g., indicating a potential us of the currentdevice due to the proximity of a supported UE.

At 720, method 700 can comprise selecting a device state update based onan input related to an operation profile, historical use data, andsupplementary data. Once the device is determined to be eligible for astate transition and that the current use satisfies the related rulesfor imitating the state transition, the method at 720 can determine whatthat transition is based on inputs. An input can be an operator profilethat comprises information relating to what state transition should beimplemented for determined conditions. The conditions can be determinedfrom supplemental data, e.g., time, date, place, nearby events,historical use data, etc.

At 730, the device state can be adapted, e.g., transitioned, based onthe device state update determined at 720. At this point method 700 canend. The state transition determined at 720 can be applied at 730 inaccord with the eligibility and satisfaction of the rules at 710. Assuch, for example, a field RAN device can be eligible, the field RANdevice can be unused and a first layer of neighboring RAN devices canalso be unused by a UE resulting in the determination that the field RANdevice satisfies the use rules. It can then be determined, for example,that the field RAN device should enter a snooze state rather than an offor sleep state due to historical use data and the current time and day.

FIG. 8 illustrates example method 800 facilitating time-delayed changingof a device state based on a hierarchical class of the device, inaccordance with aspects of the subject disclosure. Method 800, at 810,can comprise receiving, by a small cell device, e.g., a RAN device,etc., an indication of a change in use of a neighboring small celldevice, wherein the neighboring small cell device is a neighbor of thesmall cell device, e.g., it can be indicated that a UE is now using aneighboring RAN device to a RAN device of interest. In the alternative,an indication of a change in the use of the small cell device itself canbe received, e.g., a UE can be attempting to directly use the small celldevice itself rather than being handed over from another device.

At 820, the small cell device state can be adapted in response to thereceiving the indication at 810. As an example, where a first small celldevice is in sleep mode, a controller device can receive an indicationthat a second small cell device, that is a neighbor to the first smallcell device, has started to support a UE. The example controller canthen adapt the state of the first small cell device, e.g., from thesleep state to another state, such as a wake state, full power state,etc. In the example, the first small cell device can be woken up inresponse to a UE moving closer to the first small cell device, whereincloser is indicative of a number of hops between the UE and the firstsmall cell device. In an aspect, closer can also indicate that the UE isphysically closer to the first small cell device because neighboringsmall cells can be closer together in distance as well as in number ofhops between them. In some instances, a closer neighbor in hops willhave a greater distance, but this can still be considered moving closerto the first small cell device due to the decrease in hops to the UE.

At 830, a timer value can be updated. At this point method 800 can end.The time value can be related to restricting subsequent adaptations ofthe small cell device state. This can reduce ‘fluttering’ where the RANdevice cyclically transitions between states without remaining in anyone state long enough to be meaningfully useful in the network ofdevices comprising the RAN device. As an example, where a small celldevice is adapted to a full power state, the time can keep the device infull power state for a few seconds to a few hours, etc. Thus, where aneighboring small cell starts supporting a UE, the first small cell canbe activated and remain on in accord with the timer. Thus, if the UEmoves away and then comes closes again, such as where the user iswalking out of their office to use the restroom and then comes back, thefirst small cell can be prevented from going to sleep during that shortperiod where the UE was outside of the service area of the neighboringsmall cell. This can be similar to preventing your desktop computer fromhibernating the second you stop using it which, if it occurred, couldwaste more time going in and out of hibernation that is acceptable,e.g., it can be cheaper to waste a short period of energy than to wastetime waiting for state transitions to occur. The timer value can beadapted based on input associated with a user identity, e.g., the timercan be set by a systems administrator, an operator, can be adapted basedon inference or machine learning techniques, can be based on historicaluse data, etc.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900comprises one or more remote component(s) 910. The remote component(s)910 can be hardware and/or software (e.g., threads, processes, computingdevices). In some embodiments, remote component(s) 910 can core networkdevices associated with a network provider identity, can be a macro RANdevice, e.g., 102, 202, 302, 402, etc., UE 304, a device generatinginput(s) 570, etc.

The system 900 also comprises one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can comprise RAN devices, 110-130, 210-237, 310-338, 410-434, 540,etc., local controller devices, controller devices of RAN devices, etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.The system 900 comprises a communication framework 940 that can beemployed to facilitate communications between the remote component(s)910 and the local component(s) 920, and can comprise an air interface,e.g., Uu interface of a UMTS network, via a long-term evolution (LTE)network, etc. Remote component(s) 910 can be operably connected to oneor more remote data store(s) 950, such as a hard drive, solid statedrive, SIM card, device memory, etc., that can be employed to storeinformation on the remote component(s) 910 side of communicationframework 940. Similarly, local component(s) 920 can be operablyconnected to one or more local data store(s) 930, that can be employedto store information on the local component(s) 920 side of communicationframework 940. As examples, historical use data, supplementary data,current use data, neighboring use data, user input(s), etc., can bestored on remote data store(s) that can be comprised in or connected toa macro RAN device, e.g., 102, 202, 302, 402, etc., a UE 304, a devicegenerating input(s) 570, etc.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules comprise routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can comprise both volatile and nonvolatilememory, by way of illustration, and not limitation, volatile memory 1020(see below), non-volatile memory 1022 (see below), disk storage 1024(see below), and memory storage 1046 (see below). Further, nonvolatilememory can be included in read only memory, programmable read onlymemory, electrically programmable read only memory, electricallyerasable read only memory, or flash memory. Volatile memory can compriserandom access memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as synchronous random access memory, dynamic randomaccess memory, synchronous dynamic random access memory, double datarate synchronous dynamic random access memory, enhanced synchronousdynamic random access memory, Synchlink dynamic random access memory,and direct Rambus random access memory. Additionally, the disclosedmemory components of systems or methods herein are intended to comprise,without being limited to comprising, these and any other suitable typesof memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, comprising single-processoror multiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, a macro RANdevice, e.g., 102, 202, 302, 402, etc., a UE 304, a device generatinginput(s) 570, etc., a RAN device, 110-130, 210-237, 310-338, 410-434,540, etc., a local controller device, a controller device of a RANdevices, etc., can comprise a processing unit 1014, a system memory1016, and a system bus 1018. System bus 1018 couples system componentscomprising, but not limited to, system memory 1016 to processing unit1014. Processing unit 1014 can be any of various available processors.Dual microprocessors and other multiprocessor architectures also can beemployed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)comprising a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures comprising, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can comprise volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can compriseread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 comprises read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also comprise removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 comprises, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can comprise storage media separately or in combination with otherstorage media comprising, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, read only memory, programmable readonly memory, electrically programmable read only memory, electricallyerasable read only memory, flash memory or other memory technology,compact disk read only memory, digital versatile disk or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can comprisenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,can cause a system comprising a processor to perform operations,comprising determining, by a RAN device (110-130, 210-237, 310-338,410-434, 540, etc.), a hierarchical class, a next state, satisfaction ofa current use rule for the RAN device itself, or of a neighboring RANdevice, and employing those determinations to effect a state transitionfor the RAN device.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software comprises an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. In some embodiments, a user interface can allowentry of user preference information, etc., and can be embodied in atouch sensitive display panel, a mouse/pointer input to a graphical userinterface (GUI), a command line controlled interface, etc., allowing auser to interact with computer 1012. Input devices 1036 comprise, butare not limited to, a pointing device such as a mouse, trackball,stylus, touch pad, keyboard, microphone, joystick, game pad, satellitedish, scanner, TV tuner card, digital camera, digital video camera, webcamera, cell phone, smartphone, tablet computer, etc. These and otherinput devices connect to processing unit 1014 through system bus 1018 byway of interface port(s) 1038. Interface port(s) 1038 comprise, forexample, a serial port, a parallel port, a game port, a universal serialbus, an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a universal serial bus port can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 comprise, by way of illustration and notlimitation, video and sound cards that provide means of connectionbetween output device 1040 and system bus 1018. It should be noted thatother devices and/or systems of devices provide both input and outputcapabilities such as remote computer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, a cloud service, code executing ina cloud-computing environment, a workstation, a microprocessor basedappliance, a peer device, or other common network node and the like, andtypically comprises many or all of the elements described relative tocomputer 1012. A cloud computing environment, the cloud, or othersimilar terms can refer to computing that can share processing resourcesand data to one or more computer and/or other device(s) on an as neededbasis to enable access to a shared pool of configurable computingresources that can be provisioned and released readily. Cloud computingand storage solutions can store and/or process data in third-party datacenters which can leverage an economy of scale and can view accessingcomputing resources via a cloud service in a manner similar to asubscribing to an electric utility to access electrical energy, atelephone utility to access telephonic services, etc.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies comprise fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies comprise, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can comprise, for example, internaland external technologies such as modems, comprising regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, comprising what is described in the Abstract, is notintended to be exhaustive or to limit the disclosed embodiments to theprecise forms disclosed. While specific embodiments and examples aredescribed herein for illustrative purposes, various modifications arepossible that are considered within the scope of such embodiments andexamples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form. Moreover, the use of any particularembodiment or example in the present disclosure should not be treated asexclusive of any other particular embodiment or example, unlessexpressly indicated as such, e.g., an first embodiment that has aspect Aand a second embodiment that has aspect B does not preclude a thirdembodiment that has aspect A and aspect B. The use of granular examplesand embodiments is intended to simplify understanding of certainfeatures, aspects, etc., of the disclosed subject matter and is notintended to limit the disclosure to said granular instances of thedisclosed subject matter or to illustrate that combinations ofembodiments of the disclosed subject matter were not contemplated at thetime of actual or constructive reduction to practice.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can comprise packetized or frame-based flows. Data or signalinformation exchange can comprise technology, such as, single user (SU)multiple-input and multiple-output (MIMO) (SU MIMO) radio(s), multipleuser (MU) MIMO (MU MIMO) radio(s), long-term evolution (LTE), LTEtime-division duplexing (TDD), global system for mobile communications(GSM), GSM EDGE Radio Access Network (GERAN), Wi Fi, WLAN, WiMax,CDMA2000, LTE new radio-access technology (LTE-NX), massive MIMOsystems, etc.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks comprisebroadcast technologies (e.g., sub-Hertz, extremely low frequency, verylow frequency, low frequency, medium frequency, high frequency, veryhigh frequency, ultra-high frequency, super-high frequency, extremelyhigh frequency, terahertz broadcasts, etc.); Ethernet; X.25;powerline-type networking, e.g., Powerline audio video Ethernet, etc.;femtocell technology; Wi-Fi; worldwide interoperability for microwaveaccess; enhanced general packet radio service; second generationpartnership project (2G or 2GPP); third generation partnership project(3G or 3GPP); fourth generation partnership project (4G or 4GPP); longterm evolution (LTE); fifth generation partnership project (5G or 5GPP);third generation partnership project universal mobile telecommunicationssystem; third generation partnership project 2; ultra mobile broadband;high speed packet access; high speed downlink packet access; high speeduplink packet access; enhanced data rates for global system for mobilecommunication evolution radio access network; universal mobiletelecommunications system terrestrial radio access network; or long termevolution advanced. As an example, a millimeter wave broadcasttechnology can employ electromagnetic waves in the frequency spectrumfrom about 30 GHz to about 300 GHz. These millimeter waves can begenerally situated between microwaves (from about 1 GHz to about 30 GHz)and infrared (IR) waves, and are sometimes referred to extremely highfrequency (EHF). The wavelength (λ) for millimeter waves is typically inthe 1-mm to 10-mm range.

The term “infer” or “inference” can generally refer to the process ofreasoning about, or inferring states of, the system, environment, user,and/or intent from a set of observations as captured via events and/ordata. Captured data and events can include user data, device data,environment data, data from sensors, sensor data, application data,implicit data, explicit data, etc. Inference, for example, can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events. Inference can also refer to techniquesemployed for composing higher-level events from a set of events and/ordata. Such inference results in the construction of new events oractions from a set of observed events and/or stored event data, whetherthe events, in some instances, can be correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources. Various classification schemes and/or systems(e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, and data fusion engines) can beemployed in connection with performing automatic and/or inferred actionin connection with the disclosed subject matter.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A field radio access network device, comprising:a processor; and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations,comprising: enabling access to a parameter of the field radio accessnetwork device by a controller device; and in response to receiving anindication from the controller device, changing a state of the fieldradio access network device, wherein the changing the state of the fieldradio access network device is based on a first field radio accessnetwork device relationship between the field radio access networkdevice and a gateway radio access network device comprising a gatewayneighbor relationship with a macro radio access network device, a secondfield radio access network device relationship between the field radioaccess network device and an intermediate radio access network devicecomprising an intermediate neighbor relationship with the gateway radioaccess network device, and a third field radio access network devicerelationship between the field radio access network device and a userequipment that is not affiliated with the field radio access networkdevice and is not affiliated with a neighbor radio access network devicethat is a neighbor to the field radio access network device.
 2. Thefield radio access network device of claim 1, wherein the changing thestate of the field radio access network device results in altering apower state of the field radio access network device.
 3. The field radioaccess network device of claim 1, wherein the changing the state of thefield radio access network device results in the field radio accessnetwork device transmitting a different amount of radio frequency energythan before the initiating the state transition.
 4. The field radioaccess network device of claim 1, wherein the controller device iscomprised in the field radio access network device.
 5. The field radioaccess network device of claim 1, wherein the controller device iscomprised in a device other than the field radio access network device.6. The field radio access network device of claim 5, wherein the fieldradio access network device is a first field radio access networkdevice, and wherein the device other than the first field radio accessnetwork device controls a second field radio access network device. 7.The field radio access network device of claim 6, wherein the secondfield radio access network device comprises the controller device. 8.The field radio access network device of claim 6, wherein the secondfield radio access network device does not comprise the controllerdevice.
 9. A controller device, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: accessing aparameter of a field radio access network device; and causing the fieldradio access network device to undergo a state change, wherein the statechange is based on a first field radio access network devicerelationship between the field radio access network device and a gatewayradio access network device comprising a gateway neighbor relationshipwith a macro radio access network device, a second field radio accessnetwork device relationship between the field radio access networkdevice and an intermediate radio access network device comprising anintermediate neighbor relationship with the gateway radio access networkdevice, and a third field radio access network device relationshipbetween the field radio access network device and a user equipment thatis not affiliated with the field radio access network device and is notaffiliated with a neighbor radio access network device that is aneighbor to the field radio access network device.
 10. The controllerdevice of claim 9, wherein the state change results in altering powerconsumed by the field radio access network device.
 11. The controllerdevice of claim 9, wherein the state change results in transmitting adifferent amount of radio frequency energy via the field radio accessnetwork device than before the state change.
 12. The controller deviceof claim 9, wherein the controller device is comprised in a gatewayradio access network device.
 13. The controller device of claim 9,wherein the controller device is comprised in a macro radio accessnetwork device.
 14. The controller device of claim 9, wherein the fieldradio access network device is a first field radio access networkdevice, and wherein the controller device is comprised in a second fieldradio access network device.
 15. The controller device of claim 9,wherein the field radio access network device is a first field radioaccess network device, and wherein the controller device furthercontrols a second field radio access network device.
 16. A method,comprising: in response to receiving, by a system comprising aprocessor, a parameter of a field radio access network device,determining a first field radio access network device relationshipbetween the field radio access network device and a gateway radio accessnetwork device comprising a gateway neighbor relationship with a macroradio access network device, a second field radio access network devicerelationship between the field radio access network device and anintermediate radio access network device comprising an intermediateneighbor relationship with the gateway radio access network device, anda third field radio access network device relationship between the fieldradio access network device and a user equipment that is not affiliatedwith the field radio access network device and is not affiliated with aneighbor radio access network device that is a neighbor to the fieldradio access network device; and triggering, by the system, a statechange of the field radio access network device based on the first fieldradio access network device relationship, the second field radio accessnetwork device relationship, and the third field radio access networkdevice relationship.
 17. The method of claim 16, wherein the statechange causes the field radio access network device to consume adifferent amount of power than before the state change.
 18. The methodof claim 16, wherein the state change causes the field radio accessnetwork device to generate a different amount of radio frequency energythan before the state change.
 19. The method of claim 16, wherein thesystem comprising the processor is comprised in a gateway radio accessnetwork device.
 20. The method of claim 16, wherein the systemcomprising the processor is comprised in a device located remotely fromthe field radio access network device.